[Bitbucket] Robust datetime parsing for commit dates (#1589) #1591
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes a datetime parsing issue when reading Bitbucket Cloud commit
dates that include both an explicit timezone and a trailing 'Z', e.g.
Such values previously caused a ValueError when accessed via
Commit.date
.Related issue: #1589
Files changed
Modified:
atlassian/bitbucket/base.py
get_time()
to normalize timestamps that contain a timezonefollowed by an extraneous trailing
Z
, handle Python <3.7%z
colondifferences, and attempt multiple sensible datetime formats before
falling back.
Added:
tests/test_bug_reproduction.py
Commit
built with"2025-09-18T21:26:38+00:00Z"
returns a parsed value via.date
.